Interworking system and operation in V2X applications

ABSTRACT

A communication system and method for supporting a plurality of vehicle-to-everything radio access technologies (V2X RATs) is provided. The communication system configured to support multiple V2X RATs transmits, using a first V2X RAT, an indication of its availability to support an interworking function between the plurality of V2X RATs. The communication system receives an instruction to provide the interworking function between different V2X RATs. The interworking function may be incorporated in a vehicle that is joined to a platoon configured to use a first V2X RAT, and provide the interworking function between the first and a second V2X RAT. The interworking function may be used to add further vehicles to the platoon that communicate using only the second V2X RAT.

TECHNICAL FIELD

This disclosure relates to wireless communications, and in particular tosystems for providing interoperability between differentvehicle-to-everything (V2X) wireless communication systems.

TECHNICAL BACKGROUND

“Smart” control systems such as intelligent transportation systems relyon wireless communications between entities (e.g., ground or aerialvehicles, which may or may not be autonomously or semi-autonomouslycontrolled) to share relevant sensor and other data, and to passconfiguration and control messages, and the like. However, there existseveral possible standards for wireless communications for thesepurposes, and these standards, and the underlying technology, arecontinually evolving. This poses a challenge for operators andmanufacturers of equipment such as vehicles for intelligenttransportation systems to ensure that newer equipment continues to becompatible with older equipment.

BRIEF DESCRIPTION OF THE DRAWINGS

In drawings which illustrate by way of example only embodiments of thepresent invention,

FIG. 1 is an example network topology depicting a system for use by aplatooning application or other V2X application.

FIG. 2 is a variation of the example topology of FIG. 1.

FIG. 3 is a schematic diagram illustrating a stationary computing systemfor use in the system of FIGS. 1 and 2.

FIG. 4 is a schematic diagram of select components of a V2X-enabledvehicle.

FIG. 5 is a schematic diagram of select components of an interworkingunit such as a vehicle.

FIG. 6 is a messaging diagram illustrating advertisement of interworkingfunctions.

FIG. 7 is a messaging diagram illustrating platoon formation andconfiguration.

FIG. 8 is an illustration of a platoon in the system of FIG. 2.

FIG. 9 is a messaging diagram illustrating platoon formation orexpansion.

FIG. 10 is a messaging diagram illustrating use of an interworkingvehicle to expand a platoon.

FIG. 11 is an illustration of a further platoon in the system of FIG. 2.

FIG. 12 is a messaging diagram illustrating a measurement reportfunction of the interworking vehicle.

FIG. 13 is a messaging diagram illustrating a process for aninterworking vehicle to leave a platoon.

DETAILED DESCRIPTION OF THE INVENTION

Intelligent transportation systems, including autonomous andsemi-autonomous vehicles, are under development with the purpose ofimproving efficiency and safety. Sensor systems (e.g., radar, lidar,sonar, global positioning system (GPS), etc.) and a measure ofintelligence are added to vehicles, and even to roadside units (RSUs)(e.g., traffic light controllers), to enable vehicles to detect andreact to surrounding vehicles, obstacles, and pedestrians whileminimizing reliance on human input.

To facilitate these intelligent systems, communication amongst vehiclesand between vehicles and other entities is required: vehicle-to-vehicle(commonly referred to as V2V), vehicle-to-infrastructure, such asroadside units (V2I); with pedestrians (V2P); with electronic devices(V2D), and particularly in the case of electric or hybrid vehicles, theelectricity grid (V2G). Collectively, communications between a vehicleand another entity are referred to as vehicle-to-everythingcommunications (V2X).

However, competing development of architectures and standards forV2X—not all necessarily using the same wireless communication andtransport protocols—and continuous technological advancement posechallenges for vehicle manufacturers and operators wishing to employ anintelligent system. Consider the example of vehicle platooning orflocking. Platooning groups or links together a plurality of vehicles,which may communicate with each other to form a physical convoy thatmay, for example, drive closer together by synchronizing speed,acceleration, and braking; or drive at a constant speed. In someimplementations, one vehicle in the convoy (e.g. the lead vehicle in aline of vehicles), or a remote vehicle, server or system that is notpart of the platoon, may control the vehicles of the platoon; oralternatively, some or all of the vehicles in the platoon may beautonomously controlled. Platooning can provide efficiencies in the formof improved fuel efficiency and lower emissions (e.g., because lessbraking is required), safety (because speed and spacing between vehiclesis controlled), and more efficient road use; and, of course, if there isa human occupant in a platoon vehicle, reduced reliance on human inputin driving the vehicle may permit the human to engage in other tasksbesides driving, reduce human fatigue or enable longer continuousjourneys.

For vehicles to be part of a platoon in an intelligent transportationsystem, they need to be capable of communicating with other members oftheir platoon in order to support the cooperative behaviours required ofplatoon members. With current technology, this implies that all vehiclesin the platoon must support a common V2X radio access technology (V2XRAT). There are, however, a variety of different V2X architectures andstandards including, but not limited to, European TelecommunicationStandards Institute (ETSI) Intelligent Transport Systems (ETSI ITS),Society of Automotive Engineers (SAE) International Dedicated ShortRange Communications for Wireless Access in Vehicular Environments (SAEDSRC), and SAE International Cellular V2X (SAE C-V2X). Cellular-basedV2X (C-V2X) technologies rely on one or both of 4^(th) generationcellular/Long-Term Evolution (4G/LTE—also known as Enhanced UniversalMobile Telephony System Terrestrial Radio Access Network (E-UTRAN)) and5^(th) Generation cellular New Radio (5GNR) wireless broadbandtechnology, whereas non-cellular V2X technologies, such as ETSI ITS andSAE DSRC, are wireless local area network (WLAN) based, relying on oneor more of the IEEE 1609, IEEE 802.11bd and IEEE 802.11p standards. Eventhose V2X architectures relying on the same physical communicationtechnology may not be compatible as they may use different feature sets,transport protocols, messaging formats, and/or applications. Forexample, ETSI messaging formats include Cooperative Awareness Message(CAM) as defined in ETSI EN 302 637-2, and Decentralized EnvironmentalNotification (DENM) as defined in ETSI EN 302 637-3. Examples of SAEmessaging include Basic Safety Message (BSM) and Common Safety Request(CSR) as defined in SAE J2735. These are only a few examples; othertypes of V2X messaging may be used in various V2X systems. Current V2Xarchitectures and standards, and associated applications such asplatooning, will be known to those skilled in the art. Thus, whendifferent or distinct V2X RATs are referenced herein, these differentV2X RATs may include the same standard employing different feature sets.

Currently, it is not always feasible for all vehicles to support acommon V2X RAT, whether due to cost, or the fact that newer vehicles maybe equipped with newer-generation technology as standards are retiredand replaced, while older vehicles have not yet been decommissioned. Theresult is that vehicles with incompatible V2X RATs may not be able toparticipate together in a single platoon, thus limiting the ability of agiven vehicle to participate in platoons that may be available in agiven location, at a given time. Platoons that can be formed using acommon V2X RAT may be limited in size, as some otherwise-availablevehicles must be excluded; this may reduce overall efficiency in theoperation of the vehicles, as some of the benefits of platooning (e.g.,fuel efficiency, safety) may be reduced. Additionally, multiple platoonsmay need to be created to accommodate different V2X RATs, increasingcomputational burden on the entities managing and controlling theplatoons. Furthermore, the incompatibility in technologies may result ina first vehicle or platoon employing a first V2X RAT being unaware ofanother vehicle employing an incompatible second V2X RAT.

The need for all vehicles in a platoon to share a common V2X RAT canresult in technology “lock-in” for some operators or manufacturers, inwhich the older V2X technology is installed in newer vehicles to ensurecompatibility with existing vehicles because the cost of switching anentire fleet is deemed too high. This may slow take-up of newer orcompeting V2X technologies that may nevertheless be superior to theolder technology.

Accordingly, the following examples provide a communication system andmethod providing an interworking function between different entities(e.g., platoon entities) to extend communications from a first RAT to asecond RAT, and optionally to additional RATs. In the context of anintelligent system comprising groups of automated, autonomous orsemi-autonomous entities, the interworking function can enable theintelligent system to build a larger fleet or group of entities that areable to communicate amongst themselves even if they do not all use thesame RAT. This can be used to extend the range of cooperative andawareness messaging among entities in the intelligent system.

These concepts are set out with reference to the example system set outin FIG. 1, which schematically depicts a scenario in which one or moreplatoons of vehicles may be configured and controlled. FIG. 1 depictsseveral types of entities: operating entities 170A and 170B; managemententities 120, 130; and server system 150, which may be employed in thecontrol of one or more platoons or management entities 120, 130. Theoperating entities 170A, 170B in this example are various types ofground vehicles such as automobiles, trucks/lorries, and semi-trailertrucks/lorries; however, the operating entities need not be so limited,nor need they all be the same species. For example, the operatingentities may be, or may include, aerial vehicles, manufacturingmachinery, or other equipment, mobile machines or vehicles. Theoperating entities may be directly human-controllable (e.g., in the caseof a ground transport vehicle, occupied and driven by a human) orremotely controllable by a human, or else may be controlled by whollyautonomous or semi-autonomous systems. In the context of a platoon ofground vehicles, a typical arrangement may have a human-controlled orsemi-autonomous lead vehicle, and an accompanying set of one or moreautonomous or semi-autonomous following vehicles.

The operating entities 170A, 170B in this example are each equipped witha communication system, generally described below, enabling wirelesscommunication using at least one RAT. For example, operating entities170A may be provisioned with a communication system enabling them tocommunicate using a first RAT, whereas operating entities 170B may beprovisioned with a communication system enabling them to communicateusing a second RAT. It should be understood that the number of entities170A, 170B is not a limitation to the concepts described herein.

The first and second RATs may be differentiated by an incompatibility.For example, the first and second RATs may employ different wirelesscommunication technologies, for which the operating entities 170B, 170Aare not equipped (e.g., LTE or other cellular communication, versuswireless local area network (WLAN) communication); or, even if the RATsemploy the same wireless communication technologies, there may beincompatibility due to the use of different wireless access standards(e.g., in the context of V2X communication, ETSI ITS vs SAE DSRC); or,even where the same technologies and standards are employed, the firstand second RATs may differ by version, resulting in some incompatibilityor discontinuity in messaging or applications. This incompatibility mayprevent an operating entity 170A from communicating with an operatingentity 170B, or with the wireless infrastructure supporting operatingentity 170B, or vice versa. Thus, as illustrated in FIG. 1 by arrows,operating entities 170A may be capable of communicating with each othereither directly or via a wireless infrastructure (represented in FIG. 1by access point 160A) also capable of communicating using the same RAT;whereas operating entities 170B may be capable only of communicatingwith each other and with their corresponding wireless infrastructure160B. Generally, in these examples, it is assumed that the operatingentities are each capable of communicating amongst themselves, e.g. inthe case of vehicles, that they are all V2V capable, although they maybe restricted to a single RAT. It may be noted that in some cases, notall operating entities 170A or 170B may be able to communicate withtheir like entities 170A or 170B due to, for example, physicalconstraints. For example, successful transmission between two entities170B may not be possible due to the positions of their antennas, orobstructions.

A further entity, referred to as an interworking unit 190, is equippedwith a communication system enabling wireless communication using morethan one RAT, which may include using a single RAT with differentversions. As one example, the communication system may be capable ofusing LTE Release 14 (LTE R14) and LTE Release 15 (LTE R15) as the firstand second V2X RATs. These two versions of the same RAT haveincompatibilities for V2X operation and require special handling ascaptured in 3GPP TS 36.331. In the example of FIG. 1, the interworkingunit 190 is depicted as a stationary system capable of communicatingwith the respective wireless infrastructures 160A, 160B and through theinfrastructures, with the operating entities 170A, 170B. Theinterworking unit 190, as discussed below, can receive messagestransmitted using the first RAT from a one or more operating entities170A, and convert the messages (e.g., by reformatting) to be compatiblewith the second RAT (or convert messages from one version or release ofa single RAT to an alternative version or release, e.g. from LTE R15 toLTE R14), for transmission to one or more operating entities 170B. Theinterworking unit 190 thus provides an interworking function thatenables simultaneous access by operating entities, and other entities inthe system, to a multiplicity of RATs.

In the specific example embodiments described below, the operatingentities 170A, 170B are depicted as ground vehicles capable of executinga platooning application; thus, for the purpose of describing theseembodiments, it is presumed that the entities of FIG. 1 are platoonentities, in that they may be comprised in, or be associated with, aplatoon. It is also presumed that operating entities 170A, 170B areground vehicles and that the RATs employed are V2X RATs, and willgenerally be referred to as such in the examples below. The V2X RATs maybe selected from V2X systems currently available or available in thefuture, such as, but not limited to, ETSI ITS, SAE DSRC, and SAE C-V2X.The configuration and management of platoons, including messagingprotocols, will thus be understood by those skilled in the art.

In such scenarios, platoons may be controlled by platoon managemententities (PMEs), which determine and transmit platoon control andmanagement messages to other entities within and outside the managedplatoon. The PMEs as depicted in the accompanying drawings is anexternal computing system 120, 130, communicating over a public orprivate wide area network 100 with their respective wirelessinfrastructures represented schematically as 160A, 160B (it will beappreciated that other network entities, such as gateway systems and thelike, are omitted for ease of exposition). The PME may be a singlecomputing system as illustrated by 120, 130, or may reside in a set ofnetworked servers (e.g., a cloud service), as illustrated by service150. In some V2X implementations, the PME may be comprised in or beco-located with an RSU. The PMEs 120, 130 in this example topologycommunicate with the interworking unit 190 over the network 100. Ofcourse, it will be appreciated that suitable encryption andauthentication protocols may be used in communications between anyentities in the system to ensure safety and security. Further, somevehicles 170A, 170B, in addition to being equipped for V2Vcommunication, may also be capable of communicating with server systemssuch as 150 over the network 100, for example over a cellular radionetwork (e.g. a 4G/LTE network or a SGNR network), or over a WLAN (e.g.,IEEE 802.11p/802.11bd network).

It will be appreciated by those skilled in the art that the PME mayinstead be resident in a vehicle of the platoon, for example the leadvehicle or the interworking unit 190. In the accompanying drawings, thePME is depicted as a separate unit, but it will be understood that ifthe PME is resident in a vehicle of the platoon, or in the interworkingunit 190, communications between the PME and that vehicle or the PME andthe interworking unit may not be necessary, and may be omitted from theexamples discussed below. In other words, in the messaging diagramsdiscussed below for example, a communication with between PME 120 andthe interworking unit 190 should not be construed as limitingcommunication to a non-vehicular PME even if depicted as such. Acommunication between a PME 120 and an interworking unit 190 mayrepresent a communication between the lead vehicle of a platoon (e.g., avehicle 170A) in which the PME resides, and the interworking unit 190,even if not expressly depicted as a vehicle. Modification of theconcepts described below will be within the ability of the personskilled in the art.

Further, in the context of V2X communication, the interworking unit 190may reside in a vehicle rather than a stationary component. FIG. 2illustrates a variant of the system of FIG. 1, in which the interworkingunit 190 is comprised in a vehicle, which is therefore capable ofcommunicating with vehicles 170A and 170B, using their respective V2XRATs, and with their respective wireless infrastructures 170A, 170B. Theinterworking unit 190 may thus be in direct contact with the PME andexchange messages directly with the PME (e.g., where the PME resides ina vehicle, such as a lead vehicle of the set of vehicles 170A) and/orindirect contact with the PME (e.g., where the PME resides in a vehicle,but obstacles or interference prevent direct communication between thePME and the interworking unit; or where the PME resides in a stationarycomponent). Not all possible communication paths (vehicle-to-vehicle orvehicle-to-infrastructure) are depicted in FIG. 2. As a further example,the interworking unit 190 may be comprised in, or co-located with, anRSU. Again, the examples discussed below should not be consideredlimiting, even where the interworking unit 190 is depicted as separatefrom other vehicles. For example, communication between a PME 120 andthe interworking unit 190 may comprise vehicle-to-vehicle communication,even if not depicted as such.

FIG. 3 is a schematic representation of select functional components ofan example PME 120, whether it resides in a stationary computing systemor in a vehicle. The PME 120 is a data processing system that includesone or more microprocessors, as represented by the processing unit 210;volatile (RAM/working memory) 220 and non-volatile (NV) memory 230; andvarious input/output (I/O) subsystems 240 including human-machineinterfaces (e.g., display screens, touchscreens, keyboards, pointingdevices, and the like). These human-machine interfaces may be optional,as the PME 120 may be accessed remotely via a short range communication(e.g. Bluetooth™, Near Field Communications, ZigBee™, IEEE 802.15,Ethernet, WLAN, etc.) connection via a communication interface 260. ThePME 120 is also provided with at least one V2X RAT interface 250, whichmay include transceiver, digital signal processing, and controlcircuitry, together with one or more antennas, not illustrated in FIG.3, if the PME 120 is capable of wireless communication, as in the casewhere it resides in a vehicle. Alternatively, the PME 120 may receiveand transmit V2X messages through a gateway, not shown, using anothercommunication interface 260. The PME 120 may also communicate withexternal systems, such as cloud-based server systems and RSUs, via theother communication interfaces 260. It will be understood by thoseskilled in the art that the components illustrated in FIG. 3 are merelyrepresentative of particular aspects of the PME 120, and that othercomponents typically included in such a system, such as a power supply,buses, and other components, have been omitted from the drawings anddescription only for succinctness.

FIG. 4 is a schematic representation of an in-vehicle communicationsystem 300, including a communication system for a V2X-enabled vehiclesuch as vehicles 170A and 170B. This in-vehicle system may be built intothe vehicle in an on-board unit that interfaces with other control andmonitoring circuitry of the vehicle. One or more microprocessors(processing unit 302) control operation of the system 300. Data may bestored in either volatile 312 or non-volatile (NV) 310 memory. Thesystem 300 executes an operating system and various applications (notshown) as required, for example a platooning application to participatein platoons with other vehicles, and/or autonomous or semi-autonomousdriving. The processor unit 302 interfaces with typical elements of atransport vehicle, such as an interior touchscreen display 314 and audiosystem 316, and exterior warning system 318 and signaling features(e.g., hazard lights, headlights, sirens, horns). The processor unit 302may also be provided with an interface with one or more of the variouselectronic control units 320 in a typical vehicle controlling variousfunctions, such as the transmission, cruise control, braking systems,temperature sensors, environmental controls (e.g. heating, cooling),collision avoidance, power windows, and the like. The processing unit302 may be configured to obtain sensor and status data from one or moreof these control units—for example speed, acceleration, enginetemperature, and so on—which may be transmitted to a PME 120 or othersupervisory entity, or used by an autonomous or semi-autonomousapplication executed by the system 300 to control the vehicle.Similarly, the processing unit may also be interfaced with a powerswitch 306 controlling a power supply 304 and the vehicle ignition 308.The status of these components may also be collected by the processingunit 302. The processing unit in the vehicle includes interfaces forvarious sensors and monitoring systems in the vehicle, including radar,sonar, and/or lidar systems 322; a GPS receiver 324, and a V2X RATcommunication subsystem 326 configured to operate in accordance with agiven V2X RAT technology and version (e.g., ETSI ITS). The system 300may be provided with other wired or wireless data interfaces 328 as well(e.g., a Universal Serial Bus (USB) port, WLAN communication subsystem).Wireless communication subsystems are of course provided with antennas330, as well as any required transceivers, digital signal processors(DSPs), and control circuitry.

An interworking in-vehicle communication system 350 capable of providingthe interworking function is depicted in FIG. 5. This example alsocontemplates that the system 350 is built into a vehicle, and includesmany of the same features as the system 300 of FIG. 4. However, ratherthan a single-mode V2X RAT subsystem, the interworking system 350includes a multimode V2X RAT subsystem 340 that is capable oftransmitting and receiving messages compatible with multiple (at leasttwo) V2X RATs. Depending on which RATs are implemented, the subsystem340 may be provided with multiple antennas 330, transceivers, DSPs, andcontrol circuitry as required; but in some implementations, using thesame physical communication protocol, these elements may not need to beduplicated. In this example, the multimode V2X RAT subsystem implementsboth the SAE DSRC 360 and ETSI ITS 370 protocol stacks. When a messageis received in accordance with a first V2X RAT, the multimode subsystem340 decodes the message and determines its handling. For example, if themessage is addressed to the interworking unit 190 (e.g., an instructionto commence interworking, or an invitation to join a platoon), thesubsystem 340 may pass the message to the processing unit 302 forprocessing and execution. On the other hand, if the message is abroadcast message or addressed to another vehicle using a different RAT,the subsystem 340 may extract the message and repackage it (e.g., byreformatting the message or content values) in accordance with the otherRAT, and transmit the reformatted message for receipt by an intendeddestination.

The V2X RAT subsystem 340 may implement the interworking function withor without the processing unit 302. In some examples, the V2X RATsubsystem 340 may be included in a system-on-chip including sufficientprocessing capacity to implement the interworking function withoutrelying on the processing unit 302. Furthermore, it should be noted thatwhile the communication systems 300, 350 were depicted as on-board unitsinstalled in a vehicle including other features, the communicationsystem 300, 350 may be provided as a separate component from theprocessor unit 302, radar/sonar/lidar interface 322, and so on. Forexample, the interworking communication system consisting of themultimode V2X RAT subsystem with a dedicated processor may be providedas a plug-in component or card to be installed in a vehicle that isalready provisioned with the other elements depicted in FIG. 5. Further,the interworking communication system, with or without the additionalcomponents, may be provided in a portable wireless device that iscapable of interfacing with various on-board vehicle sensors and controlsystems.

FIG. 6 illustrates different examples of interworking unit 190advertisement of its interworking capabilities. As a first example, whenthe interworking unit 190 registers itself with a registration databaseor server system (such as the server system 150) by sending aregistration message 405 using at least one V2X RAT over the network100, its capabilities are included in an indication in its registrationinformation along with identifying information. Identifying informationcan include one or more of a digital certificate, an InternationalMobile Equipment Identity (IMEI), IMEI with software version (IMEI-SV),an International Mobile Subscriber Identity (IMSI), or some othersuitable identifier. The interworking capabilities included in theregistration message may include an identification of the specific V2XRATs supported by the interworking unit 190, and optionally anindication whether the interworking unit 190 is currently providing theinterworking function and/or its geographic location. If theinterworking unit 190 is a vehicle that is currently a member of aplatoon, the identifying information may also include an identifier forthe platoon, and optionally information about the position of theinterworking unit 190 in the platoon. Identifying information for aplatoon may be an alphanumeric identifier.

Optionally, registration by the interworking unit 190 may be triggeredby an event, as indicated by trigger 400. For example, the interworkingunit 190 may be triggered to register itself with the server system 150upon arrival at a predetermined location (e.g., an embarkation yard), orwhen a vehicle comprising the interworking unit 190 is ready to join aplatoon. For example, sensors in a transport vehicle may detect when acontainer has been attached, or when the fuel tank has been filled. Thisevent may trigger the interworking unit 190 registering with the serversystem 150. The registration system (e.g. server system 150) may respondwith configuration instructions, for example whether the interworkingunit 190 is to be configured to make interworking functions available ornot.

The interworking capability of the interworking unit 190 may thus berecorded by the server system 150, and an acknowledgment message 410 isreturned. Subsequently, a PME 120 that is assembling a platoon, orcurrently controlling a platoon, may become aware of the interworkingunit 190 by querying 415 the server system 150 for nearby or availablevehicles or interworking units. The response 420 from the server system150 can include an indication of the availability of the interworkingunit 190. Subsequently, the PME 120 may request the interworking unit190 to provide an interworking function and/or join the platoon asdiscussed below.

Alternatively or additionally, the interworking unit 190 may advertiseits capabilities by transmitting 425 its identifying information andindication, for example in a capability indication message ofinterworking capabilities, as described above, to multiple vehicles170A, 170B or PMEs 120 within communications range, using one or more ofthe V2X RATs that it supports. Generally, depending on the particularV2X protocol employed, such transmissions may or may not receive aresponse 430; in some cases, a receiving vehicle or PME may onlytransmit a response if it has determined that it is “interested” in theinterworking feature, for example if it is a PME that has determinedthat it is able to expand its platoon.

As another example, not illustrated in FIG. 6, advertisement of theinterworking unit 190's capabilities may not be transmitted directly bythe interworking unit 190. Rather, if the interworking unit 190 hasjoined a platoon and indicated its interworking capabilities to the PME120, the PME 120 or another vehicle in the platoon may instead transmitmessages to recipients (other platoon entities, or entities outside theplatoon) to announce the availability of an interworking function.

As mentioned above, the indication sent by the interworking unit 190 maybe sent using one or more of the V2X RATs that the interworking unit 190supports. As an example, an existing messaging protocol (e.g. IEEE1609.2 messaging, ETSI BTP/GN messaging, IEEE 1609 WSA and WSMPmessaging, CAM messaging, etc) may be adapted to include pertinent data.Tables 1 to 4 below show example modifications that may be made to someexisting protocols to provide an indication whether the sender of themessage currently has an interworking function active and what V2Xtechnologies are supported. Table 1 illustrates the examplemodifications/updates to the MIB in IEEE 802.11bd, for different V2Xtechnologies at a higher level perspective; Table 2 illustrates theexample modifications/updates to MIB in IEEE 802.11bd for different V2Xtechnologies at a lower level (more precisely identifying V2X messagingprotocols).

TABLE 1 Example modification to MAC and PHY MIB in IEEE 802.11bd fordifferent V2X technologies. In the dotStationConfig TABLE of Annex D,add the following to the base of the dot11StationConfigEntry sequencelist as follows: Dot11StationConfigEntry ::= SEQUENCE { . . .dot11V2XinterworkingActive TruthValue,dot11V2XtechnologySupportedETSIITS TruthValue,dot11V2XtechnologySupportedSAEDSRC TruthValue,dot11V2XtechnologySupportedSAECV2X TruthValue }

TABLE 2 Further example modification to MAC and PHY MIB in IEEE 802.11bdfor different V2X technologies. In the dotStationConfig TABLE of AnnexD, add the following to the base of the dot11StationConfigEntry sequencelist as follows: Dot11StationConfigEntry ::= SEQUENCE { . . .dot11V2XinterworkingActive TruthValue,dot11V2XtechnologySupportedR14LTEPC5 TruthValue,dot11V2XtechnologySupportedR15LTEPC5 TruthValue,dot11V2XtechnologySupportedR16NRPC5 TruthValue,dot11V2XtechnologySupportedETSIBTPGN TruthValue,dot11V2XtechnologySupportedIEEE16093 TruthValue }

Tables 3 and 4 illustrate the example modifications/additions to ETSICooperative Awareness Messaging (CAM), as set out in ETSI EN 302 637-2,Annex A. Some unchanged content is redacted for brevity. Table 3 setsout information at a higher level, while Table 4 sets out more precisedetails. Again, both include an indication whether the sender of themessage currently has an interworking function active.

TABLE 3 Example modification to ETSI CAM messaging in ETSI EN 302 637-2for different V2X technologies. CAM-PDU-Descriptions { itu-t (0)identified-organization (4) etsi (0) itsDomain (5) wg1 (1) en (302637)cam (2) version (2) } DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS . . .BasicContainer ::= SEQUENCE { stationType StationType, referencePositionReferencePosition, . . ., v2XinterworkingVehicleIndicationV2XinterworkingVehicleIndication } . . . RSUContainerHighFrequency ::=SEQUENCE { protectedCommunicationZonesRSU ProtectedCommunicationZonesRSUOPTIONAL, . . . } V2XinterworkingVehicleIndication ::= SEQUENCE {interworkingActivated NULL OPTIONAL,supportedV2XiwTechnologiesAndCapabilitiesV2XiwTechnologiesAndCapabilitres, . . . }V2XiwTechnologiesAndCapabilities ::= SEQUENCE { ETSI-ITS NULL OPTIONAL,SAE-DSRC NULL OPTIONAL, SAE-C-V2X NULL OPTIONAL, . . . }GenerationDeltaTime ::= INTEGER { oneMilliSec(1) } (0..65535) END

TABLE 4 Further example modification to ETSI CAM messaging in ETSI EN302 637-2 for different V2X technologies. CAM-PDU-Descriptions { itu-t(0) identified-organization (4) etsi (0) itsDomain (5) wg1 (1) en(302637) cam (2) version (2) } DEFINITIONS AUTOMATIC TAGS ::= BEGINIMPORTS . . . BasicContainer ::= SEQUENCE { stationType StationType,referencePosition ReferencePosition, . . .,v2XinterworkingVehicleIndication V2XinterworkingVehicleIndication } . .. RSUContainerHighFrequency ::= SEQUENCE {protectedCommunicationZonesRSU ProtectedCommunicationZonesRSU OPTIONAL,. . . } V2XinterworkingVehicleIndication ::= SEQUENCE {interworkingActivated NULL OPTIONAL,supportedV2XiwTechnologiesAndCapabilitiesV2XiwTechnologiesAndCapabilities, . . . }V2XiwTechnologiesAndCapabilities ::= SEQUENCE { v2XiwTechnologiesV2XiwTechnologies OPTIONAL, v2XiwCapabilities V2XiwCapabilitiesOPTIONAL, . . . } V2XiwTechnologies ::= SEQUENCE { r14LTEPC5 NULLOPTIONAL, r15LTEPC5 NULL OPTIONAL, r16NRPC5 NULL OPTIONAL, IEEE802-11pNULL OPTIONAL,  IEEE802-11bd NULL OPTIONAL, . . . } V2XiwCapabilities::= SEQUENCE { ETSIBTP-GN NULL OPTIONAL, IEEE1609-3 NULL OPTIONAL, . . .} GenerationDeltaTime ::= INTEGER { oneMilliSec(1) } (0..65535) END

Table 5 sets out an example messaging modification to IEEE 1609.3 toindicate support for different V2X technologies and to indicate whetherthe sender of the message currently has an interworking function active.Table 6 sets out the values and descriptions for the Capabilitysub-field in Table 5. Tables 7 and 8 set out a more detailedmodification to IEEE 1609.3, with more robust details concerning V2X RATsupport set out in the Capability sub-field.

TABLE 5 Example interworking indication modification for IEEE 1609.3.WAVE Element Information ID = 9 Length Capability (optional) Octets 1 12 variable

TABLE 6 Sub-field format for Capability octets of Table 5. Bitmap valueDescription Bit 0 (MSB) ETSI-ITS supported Bit 1 SAE-DSRC supported Bit2 SAE-CV2X supported Bit 3-15 Reserved

TABLE 7 Example interworking indication modification for IEEE 1609.3.WAVE Element Information ID = 10 Length Capability (optional) Octets 1 14 variable

TABLE 8 Sub-field format for Capability octets of Table 7. Bitmap valueDescription Bit 0 (MSB) R14 LTE PC5 supported Bit 1 R15 LTE PC5supported Bit 2 R16 NR PC5 supported Bit 3 ETS IBT PGN supported Bit 4IEEE 1609.3 supported Bit 5-31 Reserved

Tables 9 and 10 set out example modifications to the Radio ResourceControl (RRC) protocol as used on the PC5 interface specified by 3GPP TS36.331 (subclause 6.3.8, Sidelink information elements) to indicate whatV2X RATs are supported and whether interworking is currently active.Again, the second table, Table 10, sets out more detailed supportinformation for the interworking function.

TABLE 9 Example modification to sidelink information in RRC protocol asdefined in 3GPP TS 36.331. 6.3.8 Sidelink information elements . . . - SL-V2XinterworkingVehicleIndication The IESL-V2XinterworkingVehicleIndication indicates information relating to aUE's capability of V2X technology interworking.SL-V2XinterworkingVehicleIndication information element -- ASN1STARTSL-V2XinterworkingVehicleIndication-r15 ::= SEQUENCE {interworkingActivated-r15 BOOLEAN,supportedV2XiwTechnologiesAndCapabilities-r15 SL-iwTechnologiesAndCapabilities-r15, . . . }SL-iwTechnologiesAndCapabilities-r15 ::= SEQUENCE { ETSI-ITS-r15ENUMERATED {supported} OPTIONAL, SAE-DSRC-r15 ENUMERATED {supported}OPTIONAL, SAE-C-V2X-r15 ENUMERATED {supported} OPTIONAL, . . . } --ASN1STOP SL-V2XinterworkingVehicleIndication field descriptionsinterworkingActivated Indicates whether the source UE is currentlyperforming V2X interworking between two or more V2X technologiesETSI-ITS Indicates support by the sender the capability of interworkingto and from ETSI ITS V2X technology. SAE-DSRC Indicates support by thesender the capability of interworking to and from SAE DSRC V2Xtechnology.

TABLE 10 Example modification to sidelink information in RRC protocol asdefined in 3GPP TS 36.331. 6.3.8 Sidelink information elements . . . -  SL-V2XinterworkingVehicleIndication The IESL-V2XinterworkingVehicleIndication indicates information relating to aUE's capability of V2X technology interworking.SL-V2XinterworkingVehicleIndication information element -- ASN1STARTSL-V2XinterworkingVehicleIndication-r15 ::= SEQUENCE {interworkingActivated BOOLEAN, supportedV2XiwTechnologiesAndCapabilitiesSL- iwTechnologiesAndCapabilities-r15, . . . }SL-iwTechnologiesAndCapabilities-r15 ::= SEQUENCE { v2XiwTechnologiesSL-V2XiwTechnologies-r15 OPTIONAL, v2XiwCapabilitresSL-V2XiwCapabilities-r15 OPTIONAL, . . . } SL-V2XiwTechnologies-r15 ::=SEQUENCE { r14LTEPC5-r15 ENUMERATED {supported} OPTIONAL, r15LTEPC5-r15ENUMERATED {supported} OPTIONAL, r16NRPC5-r15 ENUMERATED {supported}OPTIONAL, IEEE802-11p-r15 ENUMERATED {supported} OPTIONAL, IEEE802-11bd-r15 ENUMERATED {supported} OPTIONAL, . . . }SL-V2XiwCapabilities-r15 ::= SEQUENCE { ETSIBTP-GN-r15 ENUMERATED{supported} OPTIONAL, IEEE1609-3-r15 ENUMERATED {supported} OPTIONAL, .. . } -- ASN1STOP SL-V2XinterworkingVehicleIndication field descriptionsinterworkingActivated Indicates whether the source UE is currentlyperforming V2X interworking between two or more V2X technologiesr14LTEPC5 Indicates support by the sender the capability of interworkingto and from Rel-14 LTE- based PC5. r15LTEPC5 Indicates support by thesender the capability of interworking to and from Rel-15 LTE- based PC5.r16NRPC5 Indicates support by the sender the capability of interworkingto and from Rel-16 NR- based PC5. IEEE802-11p Indicates support by thesender the capability of interworking to and from IEEE 802.11p.IEEE802-11bd Indicates support by the sender the capability ofinterworking to and from IEEE 802.11bd. ETSIBTP-GN Indicates support bythe sender the capability of interworking to and from ETSI BTP/GN.IEEE1609-3-2010 Indicates support by the sender the capability ofinterworking to and from IEEE 1609.3- 2010

Tables 11 and 12 set out example modifications to the RRC protocol asused on the Uu interface as defined in 3GPP TS 36.331, again indicatingwhat V2X RATs are supported and whether interworking is currentlyactive, and where Table 12 sets out support in greater detail.

TABLE 11 Example modification to the RRC protocol as used on the Uuinterface as defined in 3GPP TS 36.331. 6.3.6 Other information elements. . . - UE-EUTRA-Capability The IE UE-EUTRA-Capability is used to conveythe E-UTRA UE Radio Access Capability Parameters, see TS 36.306, and theFeature Group Indicators for mandatory features (defined in Annexes B.1and C.1) to the network. The IE UE-EUTRA-Capability is transferred in E-UTRA or in another RAT. NOTE 0: For (UE capability specific) guidelineson the use of keyword OPTIONAL, see Annex A.3.5. UE-EUTRA-Capabilityinformation element -- ASN1START UE-EUTRA-Capability ::= SEQUENCE { accessStratumRelease AccessStratumRelease,  ue-Category INTEGER (1..5), pdcp-Parameters PDCP-Parameters,  phyLayerParametersPhyLayerParameters,  rf-Parameters RF-Parameters,  measParametersMeasParameters,  featureGroupIndicators BIT STRING (SIZE (32)) OPTIONAL, interRAT-Parameters SEQUENCE { utraFDD IRAT-ParametersUTRA-FDDOPTIONAL, utraTDD128 IRAT-ParametersUTRA-TDD128 OPTIONAL, utraTDD384IRAT-ParametersUTRA-TDD384 OPTIONAL, utraTDD768IRAT-ParametersUTRA-TDD768 OPTIONAL, geran IRAT-ParametersGERANOPTIONAL, cdma2000-HRPD IRAT-ParametersCDMA2000-HRPD OPTIONAL,cdma2000-1xRTT IRAT-ParametersCDMA2000-1XRTT OPTIONAL  }, nonCriticalExtension UE-EUTRA-Capability-v920-IEs OPTIONAL } -- Latenon critical extensions UE-EUTRA-Capability-v9a0-IEs ::= SEQUENCE { featureGroupIndRel9Add-r9 BIT STRING (SIZE (32)) OPTIONAL, fdd-Add-UE-EUTRA-Capabilitres-r9 UE-EUTRA-CapabilityAddXDD-Mode- r9OPTIONAL,  tdd-Add-UE-EUTRA-Capabilities-r9UE-EUTRA-CapabilityAddXDD-Mode- r9 OPTIONAL,  nonCriticalExtensionUE-EUTRA-Capability-v1500-IEs OPTIONAL } UE-EUTRA-Capability-v1500-IEs::= SEQUENCE {  phyLayerParameters-v1500 PhyLayerParameters-v1500, . . . mbms-Parameters-v1500 MBMS-Parameters-v1500 OPTIONAL, sl-Parameters-v1500 SL-Parameters-v1500 OPTIONAL,  . . .OPTIONAL }SL-Parameters-v1500 ::= SEQUENCE { sl-v2xinterworkingVehicleIndication-r15 SL-V2XinterworkingVehicleIndication-r15 OPTIONAL }SL-V2XinterworkingVehicleIndication-r15 ::= SEQUENCE { interworkingActivated-r15 BOOLEAN, supportedV2XiwTechnologiesAndCapabilities-r15 SL-iwTechnologiesAndCapabilities-r15,  . . . }SL-iwTechnologiesAndCapabilities-r15 ::= SEQUENCE {  ETSI-ITS-r15ENUMERATED {supported}  OPTIONAL,  SAE-DSRC-r15 ENUMERATED {supported} OPTIONAL,  SAE-C-V2X-r15 ENUMERATED {supported}  OPTIONAL,  . . . } --ASN1STOP SL-V2XinterworkingVehicleIndication Indicates informationrelating to a UE's capability of V2X technology interworking.interworkingActivated Indicates whether the source UE is currentlyperforming V2X interworking between two or more V2X technologiesETSI-ITS Indicates support by the sender the capability of interworkingto and from ETSI ITS V2X technology. SAE-DSRC Indicates support by thesender the capability of interworking to and from SAE DSRC V2Xtechnology.

TABLE 12 Example modification to the RRC protocol as used on the Uuinterface as defined in 3GPP TS 36.331. 6.3.6 Other information elements. . . - UE-EUTRA-Capability The IE UE-EUTRA-Capability is used to conveythe E-UTRA UE Radio Access Capability Parameters, see TS 36.306, and theFeature Group Indicators for mandatory features (defined in Annexes B.1and C.1) to the network. The IE UE-EUTRA-Capability is transferred in E-UTRA or in another RAT. NOTE 0: For (UE capability specific) guidelineson the use of keyword OPTIONAL, see Annex A.3.5. UE-EUTRA-Capabilityinformation element -- ASN1START UE-EUTRA-Capability ::= SEQUENCE { accessStratumRelease AccessStratumRelease,  ue-Category INTEGER (1..5), pdcp-Parameters PDCP-Parameters,  phyLayerParametersPhyLayerParameters,  rf-Parameters RF-Parameters,  measParametersMeasParameters,  featureGroupIndicators BIT STRING (SIZE (32)) OPTIONAL,  interRAT-Parameters SEQUENCE { utraFDDIRAT-ParametersUTRA-FDD  OPTIONAL, utraTDD128 IRAT-ParametersUTRA-TDD128 OPTIONAL, utraTDD384 IRAT-ParametersUTRA-TDD384  OPTIONAL, utraTDD768IRAT-ParametersUTRA-TDD768  OPTIONAL, geran IRAT-ParametersGERANOPTIONAL, cdma2000-HRPD IRAT-ParametersCDMA2000-HRPD  OPTIONAL,cdma2000-1xRTT IRAT-ParametersCDMA2000-1XRTT  OPTIONAL  }, nonCriticalExtension UE-EUTRA-Capability-v920-IEs  OPTIONAL } -- Latenon critical extensions UE-EUTRA-Capability-v9a0-IEs ::= SEQUENCE { featureGroupIndRel9Add-r9  BIT STRING (SIZE (32))  OPTIONAL, fdd-Add-UE-EUTRA-Capabilities-r9 UE-EUTRA-CapabilityAddXDD-Mode- r9OPTIONAL,  tdd-Add-UE-EUTRA-Capabilities-r9UE-EUTRA-CapabilityAddXDD-Mode- r9 OPTIONAL,  nonCriticalExtensionUE-EUTRA-Capability-v1500-IEs  OPTIONAL } UE-EUTRA-Capability-v1500-IEs::= SEQUENCE {  phyLayerParameters-v1500  PhyLayerParameters-v1500, . ..  mbms-Parameters-v1500  MBMS-Parameters-v1500  OPTIONAL, sl-Parameters-v1500  SL-Parameters-v1500  OPTIONAL,  . . .OPTIONAL }SL-Parameters-v1500 ::= SEQUENCE { sl-v2xinterworkingVehicleIndication-r15 SL-V2XinterworkingVehicleIndication-r15  OPTIONAL }SL-V2XinterworkingVehicleIndication-r15 ::= SEQUENCE { interworkingActivated BOOLEAN, supportedV2XiwTechnologiesAndCapabilities SL-iwTechnologiesAndCapabilities-r15,  . . . }SL-iwTechnologiesAndCapabilities-r15 ::= SEQUENCE {  v2XiwTechnologiesSL-V2XiwTechnologies-r15  OPTIONAL,  v2XiwCapabilitiesSL-V2XiwCapabilities-r15  OPTIONAL,  . . . } SL-V2XiwTechnologies-r15::= SEQUENCE {  r14LTEPC5-r15 ENUMERATED {supported}  OPTIONAL, r15LTEPC5-r15 ENUMERATED {supported}  OPTIONAL,  r16NRPC5-r15ENUMERATED {supported}  OPTIONAL,  IEEE802-11p-r15 ENUMERATED{supported}  OPTIONAL,  IEEE802-11bd-r15 ENUMERATED {supported} OPTIONAL,  . . . } SL-V2XiwCapabilities-r15 ::= SEQUENCE { ETSIBTP-GN-r15 ENUMERATED {supported}  OPTIONAL,  IEEE1609-3-r15ENUMERATED {supported}  OPTIONAL,  . . . } -- ASN1STOPSL-V2XinterworkingVehicleIndication field descriptionsinterworkingActivated Indicates whether the source UE is currentlyperforming V2X interworking between two or more V2X technologiesr14LTEPC5 Indicates support by the sender the capability of interworkingto and from Rel-14 LTE-based PC5. r15LTEPC5 Indicates support by thesender the capability of interworking to and from Rel-15 LTE-based PC5.r16NRPC5 Indicates support by the sender the capability of interworkingto and from Rel-16 NR-based PC5. IEEE802-11p Indicates support by thesender the capability of interworking to and from IEEE 802.11p.IEEE802-11bd Indicates support by the sender the capability ofinterworking to and from IEEE 802.11bd. ETSIBTP-GN Indicates support bythe sender the capability of interworking to and from ETSI BTP/GN.IEEE1609-3-2010 Indicates support by the sender the capability ofinterworking to and from IEEE 1609.3-2010

These example modifications are, of course, not exhaustive.Modifications may be made in different ways to achieve the same result.

The availability of the interworking unit 190 having been indicated toother entities in the system, a next step may be the configuration of anew platoon. The formation of a platoon may be automatic (“dynamicplatoon forming”), or manual, for example with human intervention(“static platoon forming”), or a combination of both dynamic and staticforming (“semi-static platoon forming”, “semi-dynamic platoon forming”).This may be done, as in the example of FIG. 7, using platoon managemententity, which may be resident in a vehicle, or within a server (e.g.,the server 120) or in a cloud-based service (e.g., system 150). In thisexample, the PME 120 is illustrated as a separate entity to a vehicle(e.g., interworking unit 190, which may be a vehicle, or vehicles 170A)but as discussed above, the example implementation in FIG. 7 is notlimiting, and modifications can be made, which will be within scope ofthe person skilled in the art.

The PME 120 controls various aspects of the platoon, such as itsmembership, member status, and configuration, and communicates platoonconfiguration parameters to all members of the platoon and any otherentity or application to be used in controlling or communicating to theplatoon. The platoon itself may be composed of vehicles having differentparameters and capabilities, as may be determined by the PME. Parametersand capabilities can include vehicle size (e.g. one or more dimensionsof the vehicle), a destination (e.g. one or more GPS co-ordinates, oneor more predetermined values that relate to a specific place, etc),route waypoints (e.g. one or more GPS co-ordinates, one or morepredetermined values that relate to a specific place, etc), number ofantennas, antenna radiation pattern, antenna height (e.g. in measurementunits (e.g. millimeters)), and so forth. In these embodiments, theplatoon can include vehicles using different communication technologiesor feature sets. The PME 120 may use information about the parametersand capabilities of individual vehicles, as well as information aboutvehicles or other entities capable of acting as an interworking unit190, to create a platoon using more than one V2X RAT (e.g., more thanone communication protocol or feature set) by relying on theinterworking unit 190 to ensure communications between differentvehicles with different communications characteristics.

FIG. 7 sets out an example interaction in a simple case between a PME120, a server system 150, the interworking unit 190, and vehicles 170A(a set of 1 . . . n vehicles in this example) communicating using afirst V2X RAT. As an initial step to create or increase the size of anexisting platoon, the PME 120 may transmit an invitation oradvertisement 500, identifying itself and the intention to form aplatoon and/or increase the size of an existing platoon. The invitationmay include information such as start point, waypoints, and destinationpoint, and departure date/time, and any other information that isdetermined to be required to permit a receiving vehicle to respond tothe advertisement. In this simple example, the advertisement istransmitted using only a first V2X RAT and is thus received andacknowledgeable by vehicles in a first set that is configured to use thesame V2X technology, such as vehicles 170A. The advertisement messagesmay be sent several times. In a more complex example, for example addingin some steps of FIG. 9 discussed below, once an interworking functionis available to the PME 120, the PME 120 may initiate transmission ofadvertisements using one or more V2X RATs. In the example of FIG. 7, theinterworking unit 190 (which may be comprised in a vehicle) and thevehicles 170A receive the advertisement 500.

When a vehicle receiving the advertisement is capable of joining aplatoon, the vehicle 190, 170A may then verify the platoonadvertisement, and/or the PME 120 identity or location in order toensure the PME is a valid or authorized PME. This may occur by messaginga known server, such as the server system 150, and obtaining a response(optional authentication request 505 and response 510).

If the PME 120 is successfully verified, interested vehicles (includingthe interworking unit 190) may then transmit join request messages 515,520, 525 to the PME 120 indicating the availability of theinterested/sending vehicle to join the platoon, with identifyinginformation about the interested vehicle and requesting platoonmembership, and/or indicating the interested vehicle's capabilities andparameters, as described above. This message may be transmitted viaother routes through the network 100. The PME 120 may then use theidentifying information to request authenticating information about therequesting vehicles, for example from the server system 150, prior toaccepting the requesting vehicles into the platoon (optional request 530and response 535).

The join requests 515, 520, 525 may include the vehicle's capabilitiesand parameters together with the join requests, or else the additionalinformation may be sent in a separate message from the join request.Alternatively, the PME 120 may obtain this information from a separatesource such as the server system 150. Thus, if the interworking unit 190had previously registered with the server system 150 as an interworkingunit 190, the PME 120 may receive information about interworkingcapabilities from the system 150. The PME 120 uses information abouteach vehicle's capabilities and other parameters to determine membershipof the vehicle. For example, it may be desirable to build a platoonincluding specific vehicle sizes or technology capabilities, andspecifically, the PME 120 may include the interworking unit 190 in theplatoon in order to extend the range of its communications beyond thesingle V2X RAT used by the vehicles 170A.

The PME 120 then sends an invitation and/or configuration message 540 tothose vehicles accepted into the platoon. This message may comprisecommon instructions for all accepted vehicles, and can be transmitted ina broadcast or multicast; or alternatively, individual configurationmessages may be sent to each accepted vehicle, and can includeindividual instructions concerning the respective configuration of thevehicle and the vehicle's location in the platoon. Thus, for example, anindividual configuration message 540 sent to the interworking unit 190may include an instruction to activate the interworking unit 190'sinterworking function to enable the PME 120 to extend the PME 120'scommunication range to vehicles employing other technologies.Configuration messages may be transmitted directly between the PME 120and the vehicles; however, in the case where the PME 120 is outside theconvoy—for example, in a remote computing system—then configurationinformation may be disseminated within the platoon by transmissionsbetween adjacent vehicles. A direct or multicast message may be sentwith identifiers with specific recipients, whereas a broadcast messagemay be intended only for certain recipients, but received by moreentities. To restrict receipt of information to only platoon members,security measures such as encryption may be used to ensure that themessage is decryptable and readable only by the intended recipient.

Other information contained in the message may be information necessaryto configure the platoon, including establishing and configuring themembers of the platoon, plus route information such as start point,waypoints and endpoints, and timing including start and waypoint targettimes/dates. Other information in the message may include a platoonidentity, one or more identifiers associated with other vehicles in theplatoon, a primary V2X RAT supported, an indication of whether or notthere is an interworking vehicle 190 available, and if so, theinterworking vehicle 190's one or more identities, position within theplatoon, and other RATs supported, and so forth. In particular,confirmation of a V2X RAT to be used by the platoon may be useful, sinceit may confirm to a vehicle supporting more than one V2X RAT which V2Xtechnology is actually to be used, and to the platoon vehicles generallywhich protocols are to be used for message transfer with entitiesoutside of the platoon.

The configuration message 540 may be considered to be in the nature ofan invitation or request, since those vehicles receiving theconfiguration message, after determining that the message was intendedfor them, may then make a decision to join the platoon. If so, thevehicle may then transmit acknowledgment or acceptance messages 545,550, 555 to the PME 120. Each vehicle receiving and accepting aconfiguration message would then configure itself accordingly, forexample moving to its designated position in the platoon; in the case ofthe interworking unit 190, it may invoke its interworking function inresponse to an instruction to do so in the configuration message 540. Ifthe vehicle receiving the configuration message determines that it willnot join the platoon, the vehicle receiving the configuration messagemay send a rejection message to the PME 120 (not shown), which maycomprise a reason code for the rejection.

When all the vehicles for the platoon are configured, or at somepredetermined time or upon a triggering event after configuration,vehicles will form a platoon. This formation may initially start withsome pre-checks such as vehicles identifying themselves to each otherand their other platoon members along with confirming reliablecommunication status. Once any pre-checks are complete, the vehicles mayarrange themselves in a physical formation such that a lead or primaryvehicle is known and may establish itself at the head of the platoon,i.e., the front of the line of vehicles that constitute the platoon. Theother vehicles will fall in to order, if an order was received orindicated by the platoon configuration or by some other determination.Where any one vehicle has a particular position or location tooccupy—for example, the interworking vehicle 190 may be required tooccupy a specific position to ensure reliable communications throughoutthe platoon—then that vehicle will take up that position in the physicalplatoon order. Taking up this position may involve communicating to oneor more of the vehicles already in the formation, in order that they mayrecognize the positional requirements of the platoon configuration asinstructed by the PME 120 (not shown in FIG. 7).

An end result of the platoon formation and configuration described abovemay be the result depicted in FIG. 8, in which a set of vehicles 170Aand an interworking vehicle 190 have formed a platoon (as indicated bythe dashed outline). This example platoon communicates amongstthemselves and with the PME 120 using a first V2X RAT.

FIG. 9 depicts another example of platoon formation or platoon expansionusing an interworking unit 190. In this example, the PME 120 discoversthe availability of an interworking vehicle 190. This may occurgenerally as described with respect to FIG. 7, or alternatively, mayoccur when the PME 120 queries the server system 150 or other vehicleregistration system for information about available vehicles for aplatoon, or vehicles with specific capabilities (request 600 andresponse 605). The PME 120 may then instruct the interworking vehicle190 to provide the interworking function (request 610). If theinterworking unit 190 is available to fulfil the request, theinterworking unit 190 may send an acknowledgment confirming theinstruction (response 615), or send/transmit a message rejecting theinstruction, which may comprise a reason code for the rejection.Alternatively, this transaction between the PME 120 and the interworkingvehicle 190 may be a platoon advertisement and a request to join,followed by a configuration instruction to begin interworking.

With the interworking vehicle 190 in operation, the PME 120 may transmitadvertisements for the platoon using multiple V2X RATs, via theinterworking vehicle 190. For example, the PME 120 may transmit aplatoon advertisement 620 in the first V2X RAT that the interworkingvehicle 190 and other vehicles using the first V2X RAT. The interworkingvehicle 190 converts the received platoon advertisement 620 to a secondV2X RAT format, for example by extracting information from the messagein the first format, and reformatting the message in the second format.Depending on the differences between the two V2X RATs, other steps maybe required. The interworking vehicle 190 then transmits the reformattedadvertisement message 625 to other vehicles that can receive second V2XRAT messages, such as vehicles 170B. Table 13 sets out an examplemodification (a new WSMP frame) of a platoon advertisement message inIEEE 1609.3.

TABLE 13 Example frame for platoon advert. WAVE Platoon/ List of ElementInterworking Vehicle Information ID = 11 Length Unit ID IDs Location(optional) Octets 1 1 2 4 8 variable

Table 14 sets out a new platoon advertisement ANQP element based on IEEE802.11bd, which may be used to advertise the capabilities of a PME or aninterworking unit from one 802.11 station to another.

TABLE 14 Example platoon advert ANQP-element format. Platoon/ List ofInfo Interworking Vehicle Information ID Length Unit ID IDs Location(optional) Octets 2 2 2 1 8 variable

The Platoon/Interworking Unit ID is an identifier of the existing PME orthe interworking vehicle. This field also indicates whether the elementcontains information from the PME or the interworking vehicle. The Listof Vehicle IDs is a list of identifiers of the vehicle that belong tothe platoon or interworking vehicle, although this field may not be useddue to privacy reasons. The Location is the current location of the PMEor the interworking vehicle. This may be an absolute position, or arelative position offset from the location of the PME or theinterworking vehicle ID. Information is an optional field containingother information about the platoon/interworking vehicle, such assecurity information.

Join requests 630 from interested vehicles 170B may be received by theinterworking vehicle 190, then converted from the second V2X RAT formatto the first V2X RAT format, and sent to the PME 120 for processing(join request 635). If the vehicle 170B is accepted, the PME 120 wouldthen transmit configuration information as described before, again viathe interworking vehicle 190 (configuration messages 635, 640).Acceptance messages (645, 650) are transmitted back via the interworkingvehicle 190 as described above, or rejection messages, which maycomprise a reason code for the rejection.

Table 15 depicts an example new WSMP frame for the platoon join requestbased on IEEE 1609.3 to accommodate the interworking vehicle, whereVehicle ID is the identifier of the vehicle transmitting the element;Platoon/Interworking Unit ID is the identifier of the existing platoon,PME 120 or interworking vehicle 190 the requesting vehicle wishes tojoin; and the optional Information field may contain other informationabout the vehicle, such as security information.

TABLE 15 Example frame for platoon join request. WAVE Platoon/ ElementInterworking Information ID = 12 Length Unit ID (optional) Octets 1 1 4variable

In the case of either FIG. 7 or FIG. 9, the platoon was established withassistance from the interworking vehicle 190 during initial formation ofthe platoon. FIG. 10 illustrates an example of how a further vehicle mayjoin an existing platoon through an interworking vehicle 190, which mayor may not be part of the platoon. If required, initially theinterworking vehicle 190 and the PME 120 may exchange information(information exchange messages 700) so that they are aware of each otherand their capabilities. As part of this information exchange, the PME120 may instruct the interworking vehicle 190 to begin providing theinterworking function, if it is not already. This information exchangemay not be necessary if the interworking vehicle 190 was already amember of the platoon managed by the PME 120, since the PME 120 may haveobtained information about the interworking vehicle's capabilitiesearlier. It also would not be necessary if the interworking vehicle 190and PME 120 were co-located on the same vehicle.

The interworking vehicle 190 may then transmit a beacon message (beacon705) using one or more V2X RATs. FIG. 10 illustrates two V2X RATs, afirst V2X RAT compatible with vehicles 170A and a second V2X RATcompatible with vehicles 170B. The beacon 705 message may be a broadcastor multicast message to be received by any V2X-capable vehicle incommunications range, containing an invitation to join the platoon, andsetting out its interworking capabilities, and optionally capabilitiesof the platoon. An interested vehicle may send a request message to jointhe platoon. For vehicle 170B, the request message (join request 710) istransmitted to the interworking vehicle 190. Another request message(join request 715) is transmitted by the vehicle to the PME 120. In thiscase it is presumed the PME 120 is reachable using the V2X RAT used bythe requesting vehicle, for example via an access point or wirelessgateway, though the network 100. If, on the other hand, the PME 120 andthe interworking vehicle 190 are co-located on the same entity (e.g. avehicle, a server), distinct messages do not need to be sent. If thevehicle 170B making the request cannot access the PME 120, then therequest to join may be converted and forwarded by the interworkingvehicle 190 to the PME 120, generally as described with respect to FIG.9.

Both the interworking vehicle 190 and the PME 120 may then respond tothe request to join (responses 720 and 725, respectively). The responsefrom the interworking vehicle 190 and/or PME 120 may compriseconfiguration information and other details concerning the interworkingvehicle 190 and the platoon. If, on the other hand, the request to joinis rejected, the response 720 or 725 may include one or more reasoncodes or error codes indicating why the request is refused. Thus,through the interworking vehicle 190, the platoon may be expanded to addvehicles communicating using either the first or second V2X RAT.Consequently, the platoon may include vehicles using two, three, or moreV2X RATs, provided they are supported by an interworking vehicle 190 inthe platoon. This is illustrated schematically in FIG. 11, in which thevehicles 170A, 170B, and 190 form a platoon. A first subset of thevehicles of the platoon operate using a first V2X RAT, while a secondsubset of vehicles operates using a second V2X RAT. The interworkingvehicle 190 may be considered to be a member outside of theplatoon/either subset of vehicles, but bridging both subsets ofvehicles; or may be considered to be a member of the platoon/bothsubsets of vehicles. In some implementations, rather than simplypermitting individual vehicles of the second subset to join, an entiresubset of vehicles operating with the second V2X RAT may join the firstsubset through the interworking vehicle 190. This may occur, forexample, when two smaller platoons, each using a respective V2X RAT,merge together to create a super-platoon. Correspondingly when thesuper-platoon splits into smaller platoons/sub-platoons, theinterworking vehicle 190 may remain a member of one of the newsub-platoons or indeed all new sub-platoons.

It will be appreciated that using the interworking function of theinterworking vehicle 190, individual vehicles and other platoon entitiesin the platoon are able to relay messages to one another even though theindividual vehicles are using incompatible V2X RATs. Therelayed/interworked messages may be for any purpose, such as control ofthe platoon, or presentation of an audible, visual, or haptic alert toan occupant (e.g. driver) of a vehicle. The interworking vehicle 190 mayalso be used to relay/interwork information obtained from its ownplatoon to another platoon or vehicle that is not joining or not part ofa platoon. This is useful to help ensure that V2X messages (e.g. V2Xmessaging related to emergencies) are received by all affected vehicles,provided they are within communication range of the interworking vehicle190. The interworking vehicle 190 may relay/interwork messages to otherentities in the system, such as RSUs (not shown in FIG. 11) or to a basestation or access point providing access to the network 100. To furtherextend the communicating range of the interworking vehicle 190, a firstinterworking vehicle 190 in a platoon may communicate with anotherinterworking vehicle 190 in the same or a different platoon, and relaymessages to each other to thereby extend wireless coverage, even inunderground environments or areas without infrastructure deployment. Inaddition, when one or more of the V2X RATs is IEEE 802.11 (e.g., IEEE802.11p or IEEE 802.11bd), the interworking vehicle 190 may operate as amobile hotspot for other vehicles.

Table 16 sets out an example of a new WSMP frame modifying IEEE 1609.3for an interworking vehicle invitation (i.e., the beacon 705) that maybe sent by the interworking vehicle 190, where Interworking Unit ID isan identifier of the interworking vehicle 190, and the Reason Code is anexplanation why the invitation was made.

TABLE 16 Example frame for interworking vehicle invitation. WAVE ElementInterworking Reason Information ID = 13 Length Unit ID Code (optional)Octets 1 1 2 1 variable

Table 17 is an example of a new WSMP frame modifying IEEE 1609.3 for avehicle response to an interworking vehicle invitation. The Reason Codemay include an indication that the invitation was accepted, or mayinclude a reason for a rejection or another condition (e.g., apostponement of the request/joining, or poor signal).

TABLE 17 Example frame for invited vehicle response. WAVE Element ReasonInformation ID = 14 Length Vehicle ID Code (optional) Octets 1 1 2 1variable

Once vehicles are configured in a platoon, the order or location of theindividual vehicles may be determined by the PME 120 on the basis of anumber of factors. The order or location may be set at the configurationstage of platoon formation, described above. The decision to assign agiven order to a vehicle may be arbitrary and performed at any time, orbased on specific factors such as vehicle capabilities. On occasion, itmay be required to reconfigure or reorder the vehicles in a platoon, forexample to compensate for departing vehicles, environmental changes, orchanges to the capabilities of a vehicle in the platoon. For example, itmay be desirable to rearrange the location of the interworking vehicle190 within a platoon to maximize radio coverage by the interworkingvehicle 190 over the rest of the vehicles in the platoon, or to increasethe coverage of the interworking vehicle 190 outside the platoon, sothat additional vehicles using different V2X RATs may be added. Thus,factors that may determine whether to reposition a vehicle or position avehicle at a specific location within a platoon may include thecapabilities of the vehicle which indicate its ability to provide radiocommunications, such as the gain of the antennas, height of the vehicleand height/location of the antennas. These characteristics may bereported by the vehicle at the time of joining the platoon. Anotherpossible factor is received signal strength of radio transmissions fromother members of the platoon. This may be combined by a platoonmanagement function with other factors such as the vehicle's capabilitye.g. antenna height or antenna gain, to enable the platoon managementfunction to determine an optimum location for a specific vehicle withinthe platoon to maximize the reliability of communications within theplatoon and to ensure the availability of an interworking functionwithin the platoon.

To assist V2X interworking within an existing platoon, the interworkingvehicle 190 may be required to report to the PME 120 or to makedecisions about the format or order of the platoon, for example tooptimize the connectivity of all the V2X vehicles within the platoonnetwork. This may be done autonomously or in conjunction with anexisting PME 120. As input, the interworking vehicle 190 may requireinformation about the V2X RAT capabilities (which V2X RATs aresupported, which features and functions of those V2X RATs are supported,what version of the V2X RAT and/or features and functions are supported,etc.) of the other vehicles in the platoon, as well as their locationsin the platoon, in addition to other information relevant to theirability to move to a different location within the platoon.

FIG. 12 illustrates possible messaging between an interworking vehicle190, PME 120, and other vehicles of the platoon. Initially, the PME 120or another controlling entity for the platoon to which the interworkingvehicle 190 belongs transmits instructions configuring a measurementaction to be undertaken by the interworking vehicle 190 on demand, or inresponse to certain triggering events (measurement configuration message750). The measurement configuration message may identify the parametersto be measured (e.g., vehicle speed, signal strength), identification ofthe vehicles to be measured (if required), trigger events, andinstructions to filter measurements prior to reporting. Thisconfiguration message 750 may be included with the initial configurationmessage transmitted to the interworking vehicle 190 at the time itjoined the platoon, or may be transmitted in a separate message asillustrated in FIG. 12. The interworking vehicle 190 acknowledges themeasurement configuration message and confirms that configuration iscomplete (acknowledgement message 755), or transmits a message rejectingthe instruction, which may comprise one or more reason codes for therejection.

On the occurrence of a triggering event 760, which may be, for example,a request to join the interworking vehicle 190 (e.g., as described withrespect to FIG. 10); expiration of a timer; a measurement thresholdbeing exceeded, such as a reduction in signal level or quality from agiven platoon member below a specified level, or an ad hoc request fromthe PME 120, the interworking vehicle 190 obtains measurements, ifnecessary, from the other vehicles in the platoon. This may includerequests (measurement requests 765) for sensor and other operationalparameters from vehicles using the same or different V2X RATs, as shownin FIG. 12. The vehicles provide their sensor readings and other data byresponse (responses 770). In some instances, the interworking vehicle190 may collect some or all of the required data during normal operationof the platoon, as it relays/interworks messages between differentplatoon entities, and may not need to request some or all of themeasurements required. For example, signal strength and signal quality,current speed, acceleration, location etc. may be periodically exchangedbetween the vehicles in the course of the platoon's activities. In someimplementations, measurements may also be collected from vehicles withincommunications range of the interworking vehicle 190 that are notmembers of the platoon, as this information may be pertinent to adecision to reorder the platoon.

The interworking vehicle 190 then compiles a measurement report inaccordance with its configuration and transmits it to the PME 120(report 775). The PME 120 may then determine whether to reconfigure theplatoon, for example assigning new configuration parameters to one,some, or all members of the platoon. If a reconfiguration is determined,the reconfiguration instructions may then be broadcast, multicast, orsent directly to each vehicle in the platoon (reconfiguration message780). Each vehicle may acknowledge receipt of the message (not shown inFIG. 12). In response to the reconfiguration message 780, vehicles maythen perform a physical maneuver consistent with the reconfigurationinstructions (for example, change order within the platoon, close up agap or increase a cap between the vehicle and a leading or followingvehicle, etc.), then signal when reconfiguration is complete either tothe PME 120 directly, or via the interworking vehicle 190 if the vehiclerequires the interworking function to be able to communicate with thePME 120. It may also be noted that as a result of reconfiguration, theinterworking vehicle 190 may be advantageously placed in the platoon touse a further V2X RAT that it was not previously using.

Table 18 sets out an example new WSMP frame based on IEEE 1609.3 toimplement platoon reconfiguration in association with an interworkingvehicle. This message would be received by a target vehicle in theplatoon (identified by Vehicle ID) and identifies the new location towhich the vehicle should move.

TABLE 18 Example frame for platoon reconfiguration instruction. WAVEPlatoon/ Element Interworking Vehicle New Information ID = 15 LengthUnit ID ID Location (optional) Octets 1 1 2 4 8 variable

An interworking vehicle 190 may be required to cease interworkingoperations, for reasons such as, but not limited to, equipment failure,a need to conserve resources, a need to leave the platoon, etc. Aprocedure for an interworking vehicle 190 to cease interworkingoperations and/or leave a platoon is shown in FIG. 13. Initially,information is exchanged between the interworking vehicle 190 and thePME 120, in which the interworking vehicle 190 informs the PME 120 ofthe interworking vehicle's intention to leave the platoon and/or ceaseproviding the interworking function. This presumes that the interworkingvehicle 190 is capable of giving advance notice to the PME 120 of aplanned departure. Alternatively, the decision for interworking to ceasemay be made by the PME 120 (for example, because the platoon is to bereduced in size or disbanded), in which case the PME 120 would transmitan instruction to the interworking vehicle 190 to cease the interworkingfunction. In the illustrated example, however, the information from theinterworking vehicle 190 (notification 800) may include at least aprojected time of departure (the time may be zero if the interworkingvehicle 190 has already ceased providing interworking functions), andmay include information such as a reason code for the cessation ordeparture.

The interworking vehicle 190 may also transmit a beacon message to theother vehicles in the platoon (beacons 805), also notifying the othervehicles of the cessation of interworking functions. The information inthis message may be similar to the notification 800, and may includeadditional information about the platoon, such as the platoonidentifier. Each of the vehicles may send an acknowledgment (acknowledgemessage 810). As a result of the notice the vehicles may also send aquery to the PME 120 requesting updated information about the platoonstatus (status request 820).

Once the interworking vehicle 190 departs from the platoon orterminates/ceases its interworking function, it may send a finaldeparture message to the PME 102 and/or the other vehicles (updatesmessage 825). This message may include useful information for othervehicles in the platoon, such as identities/identifiers of otherinterworking vehicles that may be available, the time of departure,information about the platoon, etc. The PME may further respond to thequery by the vehicles with updated information about the platoon status(response 830). This response may include other information, such asreconfiguration instructions in view of the departure of theinterworking vehicle 190, cessation of interworking functions, orinformation about new interworking vehicles or platoons that thevehicles may choose to join.

In some instances, departure of the interworking vehicle 190 orcessation of the interworking function may occur without notice. Loss ofthe interworking function may be detected by the PME 120 whenacknowledgments or other messages are not received from those members ofthe platoon relying on the interworking vehicle 190.

Table 19 sets out an example new WSMP frame based on IEEE 1609.3 settingout a projected departure of an interworking vehicle, including anidentifier for the interworking vehicle, a time in milliseconds at whichthe departure is predicted to occur, either in absolute time or as anoffset time from the transmission of the element, and an identifier fora new interworking vehicle, if one is available and has been identified.In this example, if the Time field is set to 0, the departure hasalready occurred.

TABLE 19 Example frame for identifying departure of an interworkingvehicle from a platoon. WAVE New Element Interworking ReasonInterworking Information ID = 16 Length Unit ID Code Time Unit ID(optional) Octets 1 1 2 1 4 2 variable

The foregoing examples thus provide a communication system forsupporting a plurality of RATs, in which the communication system isconfigured to advertise its availability to provide an interworkingfunction to at least one entity in a set of one or more entities—such asa vehicle in a platoon of vehicles—configured to use a first RAT of theplurality of RATs, thus enabling the entities of the set to communicatewith others outside the set even where those others use a second RAT ofthe plurality that is incompatible with the first RAT. The interworkingfunction effectively provides at least one entity of the set withsimultaneous access to plurality of RATs, with the effect that itscommunication range is extended. This can be used to support cooperativeand awareness messaging, as may be used in intelligent systems ofautomated, autonomous or semi-autonomous entities, by enabling theentities to communicate with other entities that are using a differentRAT.

In particular, the foregoing examples provide a communication system andmethod for supporting a plurality of vehicle-to-everything radio accesstechnologies (V2X RATs), comprising: at least one microprocessorconfigured to transmit, using a first V2X RAT of the plurality of V2XRATs, to at least one platoon entity of a platoon implementing the firstV2X RAT, an indication that the communication system is available tosupport an interworking function for providing simultaneous access tothe plurality of V2X RATs, the platoon comprising at least one vehicle;and receive, using one of the plurality of V2X RATs, an instruction toprovide the interworking function. The one of the plurality of V2X RATsused to receive the instruction may be the same V2X RAT (i.e., the firstV2X RAT), or a different V2X RAT from the first V2X RAT such as a secondV2X RAT or a third V2X RAT. Different or distinct V2X RATs may comprisethe same standard employing different feature sets, or differentstandards.

In one aspect, the at least one microprocessor is further configured to,while providing the interworking function: receive, using the first V2XRAT, a first message in a first V2X RAT format; and transmit, using thesecond V2X RAT, information comprised in the first message in a secondmessage, wherein the second message is in a second V2X RAT format.

In another aspect, the indication comprises an identification of each ofthe plurality of V2X RATs; an indication whether the communicationsystem is currently providing the interworking function; and/or anidentifier for the communication system.

In further aspects, the communication system may be comprised in aportable mobile device, and/or may be comprised in a vehicle, a platoonmanagement entity, a server system, or an RSU.

In another aspect, the indication is transmitted upon a triggering eventassociated with the vehicle comprising the communication system, whereinthe triggering event comprises one of: the vehicle comprising thecommunication system arriving at a predefined location; and alterationof a configuration of the vehicle comprising the communication system.

Still further, the at least one microprocessor is further configured toreceive, using one of the plurality of V2X RATs, an instruction to jointhe platoon.

In a further aspect, where the communication system is comprised in avehicle and is a member of a platoon, the at least one microprocessor isconfigured to receive the instruction to provide the interworkingfunction from a platoon management entity, and may also receive aninstruction from the platoon management entity to alter a physicalposition of the vehicle in the platoon.

In other aspects, the at least one platoon entity is a platoonmanagement entity, and/or a stationary server; the vehicle may be aground vehicle or an aerial vehicle.

There is also provided a system and method implementing or implementedby a platoon management entity managing a first platoon of vehicles, thefirst platoon comprising members communicating using communicationsystems configured to use a first vehicle-to-everything radio accesstechnology (V2X RAT), in which a method comprises: determining that aninterworking function for providing simultaneous access to a pluralityof V2X RATs including the first V2X RAT is available from aninterworking vehicle comprising an interworking communication systemcapable of supporting the interworking function; and the platoonmanagement entity including the interworking vehicle in the firstplatoon.

In one aspect, the platoon management entity determines availability ofa further vehicle comprising a further communication system to join thefirst platoon, the further communication system being configured tocommunicate using a second V2X RAT of the plurality of V2X RATs; theplatoon management entity transmits, via the interworking communicationsystem utilizing both the first V2X RAT and a second V2X RAT of theplurality of V2X RATs, a request to join the first platoon to thefurther vehicle; and the platoon management entity receives, via theinterworking communication system, an acknowledgement from the furthervehicle; the platoon management entity including the further vehicle inthe first platoon.

In another aspect, determining that the interworking function isavailable comprises the platoon management entity receiving, from theinterworking communication system via the first V2X RAT, an indicationthat the communication system is available to support the interworkingfunction.

In a further aspect, including the interworking vehicle in the firstplatoon comprises, after receiving the indication, the platoonmanagement entity transmitting an instruction to provide theinterworking function to the interworking communication system.

In still a further aspect, determining availability of the furthervehicle to join the first platoon comprises the platoon managemententity receiving, from the interworking communication system, anindication of the availability of the further vehicle to join the firstplatoon, the further communication system in communication with theinterworking communication system; and/or determining availability ofthe further vehicle to join the first platoon comprises obtaining anindication of the availability of the further vehicle to join the firstplatoon from a server.

In another aspect, the further vehicle is a member of a second platoon,and transmitting the request to join the first platoon comprisestransmitting the request to a platoon management entity for the secondplatoon.

In still another aspect, the platoon management entity, after includingthe interworking vehicle in the first platoon, transmits an instructionto the interworking communication system to alter a physical position ofthe interworking vehicle in the first platoon.

In still a further aspect, the platoon management entity transmits afirst message to a first vehicle in the first platoon, the first messagein a first V2X RAT format using the first V2X RAT, wherein the firstvehicle is configured to communicate using the first V2X RAT; andtransmits a second message to a second vehicle in the first platoonwherein the second vehicle is configured to communicate using the secondV2X RAT, comprising transmitting the second message in a first V2X RATformat using the first V2X RAT to the interworking communication systemfor transmitting to the second vehicle.

In another aspect, the platoon management entity may detect a cessationof the interworking function; transmit, via the interworkingcommunication system, a message to the further vehicle removing thefurther vehicle from the first platoon; and remove the interworkingvehicle from the first platoon.

In another aspect, the platoon management entity detecting the cessationof the interworking function comprises receiving, from the interworkingcommunication system, an indication of cessation of the interworkingfunction.

In an aspect, the platoon management entity is comprised in a vehicle ofthe first platoon, a server system, or an RSU.

In a further aspect, the platoon management entity includes theinterworking vehicle in the platoon prior to determining that theinterworking function is available.

There is also provided a vehicle platoon, comprising a first subset ofone or more vehicles, the first subset comprising a vehicle with acorresponding communication system configured to communicate using afirst vehicle-to-everything radio access technology (V2X RAT); a secondsubset of one or more vehicles, the second subset comprising a vehiclewith a corresponding communication system configured to communicateusing a second V2X RAT from the first V2X RAT; and an interworkingvehicle comprising an interworking communication system configured tocommunicate using both the first and second V2X RAT, the interworkingcommunication system being configured to receive a first message in afirst V2X RAT format using the first V2X RAT, and to send informationcomprised in the first message in a second message in a second V2X RATformat using the second V2X RAT.

In one aspect, a communication system of a first vehicle of the firstsubset is configured to transmit the first message and a communicationsystem of a second vehicle of the second subset is configured to receivethe second message.

In a further aspect, a communication system of a first vehicle of thefirst subset is configured to transmit the first message and theinterworking communication system is configured to transmit the secondmessage to an RSU.

In another aspect, a communication system of a first vehicle of thefirst subset is configured to transmit the first message and theinterworking communication system is configured to transmit the secondmessage to a base station or access point.

In still another aspect, the interworking communication system isfurther configured to receive a third message in the second V2X RATformat using the second V2X RAT, and to send information comprised inthe third message in a fourth message in the first V2X RAT format usingthe first V2X RAT.

In some aspects, the interworking vehicle is comprised in the firstsubset or the second subset; and the platoon may comprise a platoonmanagement entity, which may be comprised in a vehicle in either thefirst or second subset. The first and second subset may comprise groundvehicles.

The examples and embodiments are presented only by way of example andare not meant to limit the scope of the subject matter described herein.Each example embodiment presented above may be combined, in whole or inpart, with the other examples. Further, variations of these exampleswill be apparent to those in the art and are considered to be within thescope of the subject matter described herein. Some steps or acts in aprocess or method may be reordered or omitted, and features and aspectsdescribed in respect of one embodiment may be incorporated into otherdescribed embodiments.

The data employed by the systems, devices, and methods described hereinmay be stored in one or more data stores. The data stores can be of manydifferent types of storage devices and programming constructs, such asRAM, ROM, flash memory, programming data structures, programmingvariables, and so forth. Code adapted to provide the systems and methodsdescribed above may be provided on many different types ofcomputer-readable media including computer storage mechanisms (e.g.,CD-ROM, diskette, RAM, flash memory, computer hard drive, etc.) thatcontain instructions for use in execution by one or more processors toperform the operations described herein. The media on which the code maybe provided is generally considered to be non-transitory or physical.

Computer components, software modules, engines, functions, and datastructures may be connected directly or indirectly to each other inorder to allow the flow of data needed for their operations. Variousfunctional units have been expressly or implicitly described as modules,engines, or similar terminology, in order to more particularly emphasizetheir independent implementation and operation. Such units may beimplemented in a unit of code, a subroutine unit, object, applet, scriptor other form of code. Such functional units may also be implemented inhardware circuits comprising custom VLSI circuits or gate arrays;field-programmable gate arrays; programmable array logic; programmablelogic devices; commercially available logic chips, transistors, andother such components. Functional units need not be physically locatedtogether, but may reside in different locations, such as over severalelectronic devices or memory devices, capable of being logically joinedfor execution. Functional units may also be implemented as combinationsof software and hardware, such as a processor operating on a set ofoperational data or instructions.

Use of any particular term should not be construed as limiting the scopeor requiring experimentation to implement the claimed subject matter orembodiments described herein. Any suggestion of substitutability of thedata processing systems or environments for other implementation meansshould not be construed as an admission that the invention(s) describedherein are abstract, or that the data processing systems or theircomponents are non-essential to the invention(s) described herein.

A portion of the disclosure of this patent document contains materialwhich is or may be subject to one or more of copyright, design, or tradedress protection, whether registered or unregistered. The rightsholderhas no objection to the reproduction of any such material as portrayedherein through facsimile reproduction of this disclosure as it appearsin the Patent Office records, but otherwise reserves all rightswhatsoever.

The invention claimed is:
 1. A communication system comprised in a firstvehicle of a platoon for supporting a plurality of vehicle-to-everythingradio access technologies (V2X RATs), comprising: at least onemicroprocessor configured to: transmit, using a first V2X RAT of theplurality of V2X RATs, to at least one platoon entity of a platoonimplementing the first V2X RAT, an indication that the communicationsystem is available to support an interworking function for providingsimultaneous access to a second V2X RAT of the plurality of V2X RATs,the platoon comprising at least one other vehicle; and receive, usingone of the plurality of V2X RATs, an instruction from a platoonmanagement entity to provide the interworking function; and receive,using one of the plurality of V2X RATs, an instruction from the platoonmanagement entity to alter a physical position of the first vehicle inthe platoon.
 2. The communication system of claim 1, wherein the atleast one microprocessor is further configured to, while providing theinterworking function: receive, using the first V2X RAT, a first messagein a first V2X RAT format; and transmit, using the second V2X RAT,information comprised in the first message in a second message, whereinthe second message is in a second V2X RAT format.
 3. The communicationsystem of claim 1, wherein the indication comprises: an identificationof each of the plurality of V2X RATs; an indication whether thecommunication system is currently providing the interworking function;and an identifier for the communication system.
 4. The communicationsystem of claim 1, comprised in a portable mobile device.
 5. Thecommunication system of claim 1, wherein the at least one microprocessoris configured to transmit the indication upon a triggering eventassociated with the first vehicle comprising the communication system,wherein the triggering event comprises one of: the first vehiclecomprising the communication system arriving at a predefined location;and alteration of a configuration of the first vehicle comprising thecommunication system.
 6. The communication system of claim 1, whereinthe at least one microprocessor is further configured to receive, usingone of the plurality of V2X RATs, an instruction to join the platoon. 7.The communication system of claim 1, wherein the at least one platoonentity is a platoon management entity.
 8. The communication system ofclaim 1, wherein the at least one platoon entity is a stationary server.9. The communication system of claim 1, wherein the plurality of V2XRATs includes at least one of ETSI ITS, SAE DSRC, and SAE C-V2X.
 10. Thecommunication system of claim 1, wherein the vehicle is a groundvehicle.
 11. The communication system of claim 1, wherein the vehicle isan aerial vehicle.
 12. A method for supporting a plurality ofvehicle-to-everything radio access technologies (V2X RATs), comprising:at least one microprocessor in a communication system comprised in afirst vehicle of a platoon transmitting, using a first V2X RAT of theplurality of V2X RATs, to at least one platoon entity of a platoonimplementing the first V2X RAT, an indication that the communicationsystem is available to support an interworking function for providingsimultaneous access to the plurality of V2X RATs, the platoon comprisingat least one other vehicle; and the at least one microprocessorreceiving, using one of the plurality of V2X RATs, an instruction from aplatoon management entity to provide the interworking function; and theat least one microprocessor receiving, using one of the plurality of V2XRATs, an instruction from the platoon management entity to alter aphysical position of the first vehicle in the platoon.
 13. The method ofclaim 12, wherein providing the interworking function comprises:receiving, using the first V2X RAT, a first message in a first V2X RATformat; and transmitting, using a second V2X RAT of the plurality of V2XRATs, information comprised in the first message in a second message,wherein the second message is in a second V2X RAT format.
 14. The methodof claim 12, wherein the indication comprises: an identification of eachof the plurality of V2X RATs; an indication whether the communicationsystem is currently providing the interworking function; and anidentifier for the communication system.
 15. The method of claim 12,wherein the communication system is comprised in a portable mobiledevice.
 16. The method of claim 12, wherein transmitting the indicationoccurs upon a triggering event associated with the first vehiclecomprising the communication system, wherein the triggering eventcomprises one of: the first vehicle comprising the communication systemarriving at a predefined location; and alteration of a configuration ofthe first vehicle comprising the communication system.
 17. The method ofclaim 12, further comprising the at least one microprocessor receiving,using one of the plurality of V2X RATs, an instruction to join theplatoon.
 18. The method of claim 12, wherein the at least one platoonentity is a platoon management entity.
 19. The method of claim 12,wherein the at least one platoon entity is a stationary server.
 20. Themethod of claim 12, wherein the plurality of V2X RATs includes at leastone of ETSI ITS, SAE DSRC, and SAE C-V2X.
 21. The method of claim 12,wherein the first vehicle is a ground vehicle.
 22. The method of claim12, wherein the first vehicle is an aerial vehicle.
 23. A methodimplemented by a platoon management entity managing a first platoon ofvehicles, the first platoon comprising members communicating usingcommunication systems configured to use a first vehicle-to-everythingradio access technology (V2X RAT), the method comprising: determiningthat an interworking function for providing simultaneous access to aplurality of V2X RATs including the first V2X RAT is available from aninterworking vehicle comprising an interworking communication systemcapable of supporting the interworking function; including theinterworking vehicle in the first platoon; and transmitting aninstruction to the interworking communication system to alter a physicalposition of the interworking vehicle in the first platoon.
 24. Themethod of claim 23, further comprising: the platoon management entitydetermining availability of a further vehicle comprising a furthercommunication system to join the first platoon, the furthercommunication system being configured to communicate using a second V2XRAT of the plurality of V2X RATs; the platoon management entitytransmitting, via the interworking communication system utilizing boththe first V2X RAT and a second V2X RAT of the plurality of V2X RATs, arequest to join the first platoon to the further vehicle; the platoonmanagement entity receiving, via the interworking communication system,an acknowledgement from the further vehicle; and the platoon managemententity including the further vehicle in the first platoon.
 25. Themethod of claim 24, wherein determining availability of the furthervehicle to join the first platoon comprises the platoon managemententity receiving, from the interworking communication system, anindication of the availability of the further vehicle to join the firstplatoon, the further communication system in communication with theinterworking communication system.
 26. The computing system of claim 25,wherein the at least one microprocessor is configured to detect thecessation of the interworking function by receiving, from theinterworking communication system, an indication of cessation of theinterworking function.
 27. The method of claim 24, wherein determiningavailability of the further vehicle to join the first platoon comprisesobtaining an indication of the availability of the further vehicle tojoin the first platoon from a server.
 28. The method of claim 24,wherein the further vehicle is a member of a second platoon, and whereintransmitting the request to join the first platoon comprisestransmitting the request to a platoon management entity for the secondplatoon.
 29. The method of claim 24, further comprising the platoonmanagement entity: detecting a cessation of the interworking function;transmitting, via the interworking communication system, a message tothe further vehicle removing the further vehicle from the first platoon;and removing the interworking vehicle from the first platoon.
 30. Themethod of claim 29, wherein the platoon management entity detecting thecessation of the interworking function comprises receiving, from theinterworking communication system, an indication of cessation of theinterworking function.
 31. The method of claim 23, wherein determiningthat the interworking function is available comprises the platoonmanagement entity receiving, from the interworking communication systemvia the first V2X RAT, an indication that the communication system isavailable to support the interworking function.
 32. The method of claim31, wherein including the interworking vehicle in the first platooncomprises, after receiving the indication, the platoon management entitytransmitting an instruction to provide the interworking function to theinterworking communication system.
 33. The method of claim 23, furthercomprising: the platoon management entity transmitting a first messageto a first vehicle in the first platoon, the first message in a firstV2X RAT format using the first V2X RAT, wherein the first vehicle isconfigured to communicate using the first V2X RAT; the platoonmanagement entity transmitting a second message to a second vehicle inthe first platoon wherein the second vehicle is configured tocommunicate using the second V2X RAT, comprising transmitting the secondmessage in a first V2X RAT format using the first V2X RAT to theinterworking communication system for transmitting to the secondvehicle.
 34. The method of claim 23, wherein the platoon managemententity is comprised in a lead vehicle of the first platoon.
 35. Themethod of claim 23, wherein the platoon management entity includes theinterworking vehicle in the platoon prior to determining that theinterworking function is available.
 36. The method of claim 23, whereinthe platoon management entity is comprised in a server system.
 37. Themethod of claim 23, wherein the platoon management entity is comprisedin a roadside unit.
 38. A computing system comprising at least onemicroprocessor managing a first platoon of vehicles, the first platooncomprising members communicating using communication systems configuredto use a first vehicle-to-everything radio access technology (V2X RAT),wherein the at least one microprocessor is configured to: determine thatan interworking function for providing simultaneous access to aplurality of V2X RATs including the first V2X RAT is available from aninterworking vehicle comprising an interworking communication systemcapable of supporting the interworking function; and include theinterworking vehicle in the first platoon; and transmit an instructionto the interworking communication system to alter a physical position ofthe interworking vehicle in the first platoon.
 39. The computing systemof claim 38, wherein the at least one microprocessor is furtherconfigured to: determine availability of a further vehicle comprising afurther communication system to join the first platoon, the furthercommunication system being configured to communicate using a second V2XRAT of the plurality of V2X RATs; transmit, via the interworkingcommunication system utilizing both the first V2X RAT and a second V2XRAT of the plurality of V2X RATs, a request to join the first platoon tothe further vehicle; receive, via the interworking communication system,an acknowledgement from the further vehicle; and include the furthervehicle in the first platoon.
 40. The computing system of claim 39,wherein determining availability of the further vehicle to join thefirst platoon comprises receiving, from the interworking communicationsystem, an indication of the availability of the further vehicle to jointhe first platoon, the further communication system in communicationwith the interworking communication system.
 41. The computing system ofclaim 39, wherein determining availability of the further vehicle tojoin the first platoon comprises obtaining an indication of theavailability of the further vehicle to join the first platoon from aserver.
 42. The computing system of claim 39, wherein the furthervehicle is a member of a second platoon, and wherein transmitting therequest to join the first platoon comprises transmitting the request toa platoon management entity for the second platoon.
 43. The computingsystem of claim 39, wherein the at least one microprocessor is furtherconfigured to: detect a cessation of the interworking function;transmit, via the interworking communication system, a message to thefurther vehicle removing the further vehicle from the first platoon; andremove the interworking vehicle from the first platoon.
 44. Thecomputing system of claim 38, wherein determining that the interworkingfunction is available comprises receiving, from the interworkingcommunication system via the first V2X RAT, an indication that thecommunication system is available to support the interworking function.45. The computing system of claim 44, wherein including the interworkingvehicle in the first platoon comprises, after receiving the indication,transmitting an instruction to provide the interworking function to theinterworking communication system.
 46. The computing system of claim 38,wherein the at least one microprocessor is further configured to:transmit a first message to a first vehicle in the first platoon, thefirst message in a first V2X RAT format using the first V2X RAT, whereinthe first vehicle is configured to communicate using the first V2X RAT;transmit a second message to a second vehicle in the first platoonwherein the second vehicle is configured to communicate using the secondV2X RAT, comprising transmitting the second message in a first V2X RATformat using the first V2X RAT to the interworking communication systemfor transmitting to the second vehicle.
 47. The computing system ofclaim 38, comprised in a lead vehicle of the first platoon.
 48. Thecomputing system of claim 38, wherein the at least one microprocessor isconfigured to include the interworking vehicle in the platoon prior todetermining that the interworking function is available.
 49. Thecomputing system of claim 38, comprised in a server system.
 50. Thecomputing system of claim 38, comprised in a roadside unit.
 51. Aplatoon, comprising: a first subset of one or more vehicles, the firstsubset comprising a first vehicle with a corresponding communicationsystem configured to communicate using a first vehicle-to-everythingradio access technology (V2X RAT); a second subset of one or morevehicles, the second subset comprising a second vehicle with acorresponding communication system configured to communicate using asecond V2X RAT; and an interworking vehicle comprising an interworkingcommunication system configured to communicate using both the first andsecond V2X RAT, the interworking communication system being configuredto receive a first message in a first V2X RAT format using the first V2XRAT, send information comprised in the first message in a second messagein a second V2X RAT format using the second V2X RAT, and to receive aninstruction from a platoon management entity to alter a physicalposition of the interworking vehicle in the platoon.
 52. The platoon ofclaim 51, wherein a communication system of the first vehicle of thefirst subset is configured to transmit the first message and acommunication system of the second vehicle of the second subset isconfigured to receive the second message.
 53. The platoon of claim 51,wherein a communication system of the first vehicle of the first subsetis configured to transmit the first message and the interworkingcommunication system is configured to transmit the second message to aroadside unit (RSU).
 54. The platoon of claim 51, wherein acommunication system of the first vehicle of the first subset isconfigured to transmit the first message and the interworkingcommunication system is configured to transmit the second message to abase station or access point.
 55. The platoon of claim 51, wherein theinterworking communication system is further configured to receive athird message in the second V2X RAT format using the second V2X RAT, andto send information comprised in the third message in a fourth messagein the first V2X RAT format using the first V2X RAT.
 56. The platoon ofclaim 51, wherein the interworking vehicle is comprised in the firstsubset.
 57. The platoon of claim 51, wherein the interworking vehicle iscomprised in the second subset.
 58. The platoon of claim 51, furthercomprising a platoon management entity.
 59. The platoon of claim 58,wherein the platoon management entity is comprised in a vehicle ineither the first subset or the second subset.
 60. The platoon of claim51, wherein the first subset and the second subset comprise groundvehicles.